DRIVER Technology Watch Report

This report is part of the Discovery Workpackage (WP4) and is the third report out of four deliverables. The objective of this report is to give an overview of the latest technical developments in the world of digital repositories, digital libraries and beyond, in order to serve as theoretical and practical input for the technical DRIVER developments, especially those focused on enhanced publications. This report consists of two main parts, one part focuses on interoperability standards for enhanced publications, the other part consists of three subchapters, which give a landscape picture of current and surfacing technologies and communities crucial to DRIVER. These three subchapters contain the GRID, CRIS and LTP communities and technologies. Every chapter contains a theoretical explanation, followed by case studies and the outcomes and opportunities for DRIVER in this field

PEER D3.1 Guidelines for publishers and repository managers on deposit, assisted deposit and self-archiving

Guidelines documenting the procedures for publisher deposit; for author assisted deposit and self-archiving, and for transfer to participating PEER repositories are presented here by Work Package (WP) 3: Repository Management and Reporting, following extensive consul- tation with both target groups

PEER D2.1 Draft report on the provision of usage data and manuscript deposit procedures for publishers and repository managers

The report on the provision of usage data and manuscript deposit procedures for publishers and repository managers sets out to establish a workflow for depositing stage-2 outputs in and harvesting logfiles from repositories to enable the research, conducted in work packages 4, 5, 6 & 7. It sets out an overall framework for including repositories, whereby a critical mass of content is made available in designated repositories to provide access to users

PEER D2.2 Final report on the provision of usage data and manuscript deposit procedures for publishers and repository managers

The Draft report on the provision of usage data and manuscript deposit procedures for publishers and repository managers, deliverable 2.1, set out to establish a workflow for depositing stage-2 outputs in and harvesting log files from repositories to enable the research envisaged in the PEER project. As that report preceded the tendering process whereby the respective research teams were selected, a number of issues were flagged for attention, particularly of the Usage research team, in WP5 and have since been referred for consultation. A significant outcome of the previous draft report was the recommendation to establish the PEER Depot as a closed intermediary repository, to receive publisher deposit in the form of both 50% of the full-text outputs, as well as 100% of the metadata outputs; and to serve as a base line control for the research process. The PEER Depot has since been established, and has come to play a significant role in the workflow developed. While the draft report set out a preliminary deposit workflow from publishers to repositories, the central role of the PEER Depot has since influenced further developments in the provision of usage data and manuscript deposit procedures for both publishers and authors. This report is the result of an ongoing negotiation between stakeholder groups comprising publishers and the library/repository community to establish best practice in deposit proce- dures that are least disruptive of existing publication workflows, while minimizing additional effort in repository ingest activities

DRIVER Guidelines 2.0 : Guidelines for content providers - Exposing textual resources with OAI-PMH (November 2008)

Vanderfeesten M, Summann F, Slabbertje M, eds. DRIVER Guidelines 2.0 : Guidelines for content providers - Exposing textual resources with OAI-PMH (November 2008).; 2008.For communication in general it is important that person B is able to understand what person A is saying. For this common understanding one needs a common ground, a basic lexicon with an awareness of the meaning of things. From this point on one can start reasoning. In order to support scholarly communication with the use of repositories, repositories should speak the same language and it is therefore essentialto create a common ground. In technical terms we create a common ground by conducting "interoperability". Interoperability can be managed at different layers. In the DRIVER Guidelines we basically try to reach interoperability on two layers, syntactical (Use of OAI-PMH & Use of OAI_DC) and semantic (Use of Vocabularies). Stand: November 200

Semanticly querying Authority Files surpass CRIS's for reporting scholarly information

<p>Introducing Semantic web technologies in the databases used by the registration of current research information, can significantly reduce manual labor, and increase precision of the data.</p> <p>A use case is presented bor performance reporting by self-evaluation at Dutch Universities.</p

Linking research articles and datasets using ORCID profiles

<p>The basic idea is to allow researchers to indicate what datasets are used in what publications, that both are listed on their ORCID profile.</p

Vrije Universiteit Amsterdam : research data essentials

Educational materials used in the course 'Research data essentials', Vrije Universiteit Amsterdam, Amsterdam, the Netherland

A deep validation process for open document repositories

Horstmann W, Vanderfeesten M, Nicolaki E, Manola N. A deep validation process for open document repositories. In: Chan L, Mornati S, eds. ELPUB2008. Open Scholarship: Authority, Community, and Sustainability in the Age of Web 2.0 - Proceedings of the 12th International Conference on Electronic Publishing. 2008: 429-431.Institutional document repositories show a systematic growth as well as a sustainable deployment. Therefore, they represent the current backbone of a distributed repository infrastructure. Many developments for electronic publishing through digital repositories are heading in the direction of innovative value-added services such as citation analysis or annotation systems. A rich service-layer based on machine-to-machine communication between value-added services and document repositories requires a reliable operation and data management within each repository. Aggregating search services such as OAISTER and BASE provide good results. But in order to provide good quality they also have to overcome heterogeneity by normalizing many of the data they receive and build specific profiles for sometimes even one individual repository. Since much of the normalization is done at the side of the service provider, it often remains unclear — maybe sometimes also to the manager of a local repository — exactly which data and services are exposed to the public. Here, an exploratory validation method for testing specification compliance in repositories is presented

Driver rehberi 2.0: İçerik sağlayıcılar için rehber -- OAI-PMH ile metinsel bilgi kaynakların keşfi

http://hdl.handle.net/11424/3147Genel anlamda iletişim için B kişisinin A kişinin söylediğini anlayabilmesi çok önemlidir. Ortak bir anlayış için ortak bir zemin, nesnelerin anlamları konusunda farkındalık sağlayan temel bir sözlüğe ihtiyaç vardır. Bu noktadan sonra kişi akıl yürütmeye başlayabilir. Açık erişim sistemleri akademik iletişimi desteklemek için aynı dili konuşmalıdır. Bu aynı zamanda ortak bir zemin yaratmak için de gereklidir. Teknik anlamda, “konuşabilirlik” sağlayarak ortak bir zemin yaratırız. Konuşabilirlik farklı katmanlarda yürütülebilir. DRIVER Rehberinde konuşabilirlik, söz dizimsel (OAI-PMH kullanımı ve OAI_DC kullanımı) ve anlamsal (terminolojinin kullanımı) olmak üzere iki temel yolla elde edilmeye çalışılmıştır. - See more at: http://openaccess.iyte.edu.tr:8080/xmlui/handle/11147/4135#sthash.hkQSKV9P.dpu